Skip to content

Conversation

@mribeirodantas
Copy link
Member

No description provided.

@netlify
Copy link

netlify bot commented Oct 25, 2023

Deploy Preview for nextflow-docs-staging ready!

Name Link
🔨 Latest commit bcf4074
🔍 Latest deploy log https://app.netlify.com/sites/nextflow-docs-staging/deploys/659be5b3bfc8df00088cadae
😎 Deploy Preview https://deploy-preview-4441--nextflow-docs-staging.netlify.app/config
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@mribeirodantas
Copy link
Member Author

LGTM? 😃

@mribeirodantas mribeirodantas requested a review from a team as a code owner April 3, 2024 14:39
@pditommaso pditommaso force-pushed the master branch 2 times, most recently from 5a93547 to 27345a6 Compare February 10, 2025 21:46
@bentsherman
Copy link
Member

Thanks Marcel for your contribution. Sorry that it was neglected for so long.

I was always unsure about which cases were actually affected by this bug, so I tested a bunch of combinations and the one added by this PR is the only failing case:

profiles {
    foo {
        process.memory = '2 GB'
        process {
            cpus = 2
        }
    }
}
$ nextflow config -profile foo
process {
   cpus = 2
}

Since we are planning to merge #4744 soon, I will incorporate this example into that PR so that I can recommend the strict config syntax as a solution. Otherwise it just looks like we are documenting a bug.

@bentsherman bentsherman deleted the fix-danger-config-docs branch February 18, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inconsistent config scope resolution when using profiles

3 participants